home *** CD-ROM | disk | FTP | other *** search
- Path: druid.borland.com!usenet
- From: pete@borland.com (Pete Becker)
- Newsgroups: comp.lang.c++
- Subject: Re: MFC or OWL?
- Date: 25 Mar 1996 19:38:39 GMT
- Organization: Borland International
- Message-ID: <4j6snv$hfm@druid.borland.com>
- References: <DKKv8H.K35@iquest.net> <4i8od1$clt@Steinlager.tip.net> <4ipmh6$79g@btree.brooktree.com> <1996Mar25.132903.546@friend.kastle.com>
- NNTP-Posting-Host: pbecker.borland.com
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=ISO-8859-1
- X-Newsreader: WinVN 0.99.5
-
- In article <1996Mar25.132903.546@friend.kastle.com>, rich@kastle.com says...
- >
- >sasha@brooktree.com (Alex Bakaev) wrote:
- >
- >>nihtila@nihtila.pp.se (Mika NihtilΣ) wrote:
- >
- >>[deleted]
- >
- >>>MFC is the industry standard...
- >
- >>Says who ? Computer press or/and uneducated managers ?
- >
- >Says virtually all Windows C++ compiler vendors. Apparently they are
- >beginning to agree with Microsoft's assertion that MFC is a de-facto
- >standard, because they are all licensing MFC for inclusion in their
- >compiler products.
-
- Yes, lots of people insist on using MFC. Whether that makes it a "standard" or
- not is up to you.
-
- >The only serious competitor to MFC was Borland's
- >OWL, but as of Borland C++ 5.0, MFC class libraries are also included.
-
- No. BC++ 5.0 can compile MFC, but it does not include the library. We still
- think OWL is a much better way to write Windows programs, and will continue to
- enhance OWL for our customers who have not been blinded by the Microsoft PR
- machine.
-
-